Method and system for coherent image group maintenance in memory

ABSTRACT

A method and system for maintaining coherent image relationships within identified image groups in a memory system of a digital image capture device includes storing a plurality of groups of related images on a removable storage device in a hierarchical manner, and providing an alias identifier for an image file when the removable storage device has reached its storage capacity, wherein the alias identifier identifies the image file stored in a storage device of the digital image capture device. The method and system further includes providing the image file with a same file name and a substitute extension designation to correlate the image file on the storage device with an empty file of the same name on the removable storage device.

RELATED APPLICATIONS

The present invention is also related to co-pending U.S. patentapplication Ser. No. 08/718,956, filed on Sep. 26, 1996, entitled AMETHOD AND SYSTEM OF GROUPING RELATED IMAGES CAPTURED WITH A DIGITALIMAGE CAPTURE DEVICE, and assigned to the assignee of the presentinvention.

The present invention is related to co-pending U.S. patent applicationSer. No. 08/718,957, filed on Sep. 26, 1996, entitled SYSTEMATIC IMAGEGROUP FORMATION, and assigned to the assignee of the present invention.

The present invention is also related to co-pending U.S. patentapplication Ser. No. 08/721,046, filed on Sep. 26, 1996, entitled METHODAND SYSTEM FOR CONTROLLED TIME-BASED IMAGE GROUP FORMATION, and assignedto the assignee of the present invention.

FIELD OF THE INVENTION

The present invention relates to digital image data processing, and moreparticularly to image group formation and control of digital image data.

BACKGROUND OF THE INVENTION

Modern digital cameras typically include an imaging device which iscontrolled by a computer system. The computer system accesses raw imagedata captured by the imaging device and then processes and compressesthe data before storing the compressed data into an internal memory. Theconventional digital camera captures raw image data and then remainsunusable until the data is completely processed and stored into internalflash memory.

In capturing raw image data, cameras exist that are capable ofperforming specific types of image captures. These image capture typesinclude time lapse captures and burst captures. Time lapse capturestypically refer to a programmed capture sequence of a particular imageover a set time period, while bursts typically refer to a rapid sequenceof image captures, i.e., a fast time lapse capture. The images capturedin time lapse sequences are thus more related than random, single imagecaptures. Of course, single image captures may also be related, such aswhen taken in a same locale, during an event, and/or of the sameperson(s). Unfortunately, the related images are not usually easilyidentified as belonging together within a computer system accessing theimage data. Further, attempts to manipulate and access these relatedimages as sets are difficult.

Accordingly, a need exists for easily identifiable image groups ofrelated images, including user-created groups.

SUMMARY OF THE INVENTION

The present invention meets these needs and provides a method and systemfor maintaining coherent image relationships within identified imagegroups in a memory system of a digital image capture device. In a methodaspect, the method includes storing a plurality of groups of relatedimages on a removable storage device in a hierarchical manner, andproviding an alias identifier for an image file when the removablestorage device has reached its storage capacity, wherein the aliasidentifier identifies the image file stored in a storage device of thedigital image capture device. The method further includes providing theimage file with a same file name and a substitute extension designationto correlate the image data on the storage device with an empty file ofthe same name on the removable storage device.

In a system aspect for maintaining coherent image relationships withinidentified image groups, the system includes a digital image capturedevice, the digital image capture device comprising removable and systemstorage devices, and further, the digital image capture device capableof processing digital image data into image files for storage in imagegroups on the removable storage device in a hierarchical manner. Thesystem also includes a central processing unit within the digital imagecapture device and capable of coordinating provision of an aliasidentifier for an image file when the removable storage device hasreached its storage capacity, wherein the alias identifier identifiesthe image file stored in the system storage device of the digital imagecapture device.

With the present invention, related images within a camera are easilyidentified through the use of image groups. The image groups areconveniently formed through command sequences that further provideparameters for the image groups, including values of tags for groupnames and group types. The parameters also provide more individualizedcontrol and greater flexibility of natural group captures. Further, withan advantageous hierarchical system for storing the groups, coordinationof image groups among memory components readily occurs, especiallyeasing management of image files in memory overflow situations.

These and other advantages of the aspects of the present invention willbe more fully understood in conjunction with the following detaileddescription and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a digital camera that operates inaccordance with the present invention.

FIG. 2 is a block diagram of the preferred embodiment for the imagingdevice of FIG. 1.

FIG. 3 is a block diagram of the preferred embodiment for the computerof FIG. 1.

FIG. 4 is a memory map showing the preferred embodiment of the read onlymemory (ROM) of FIG. 3.

FIG. 5 is a block diagram showing preferred data paths for transmittingimage data between components of the FIG. 3 computer.

FIG. 6 illustrates a hierarchical system of organizing image groups inaccordance with a preferred embodiment.

FIG. 7 illustrates a flow diagram of image group formation in accordancewith a preferred embodiment.

FIG. 8 illustrates a more detailed flow diagram of capture control inaccordance with a preferred embodiment.

DETAILED DESCRIPTION

The present invention relates to image group formation for relatedimages captured in a digital image capture device. The followingdescription is presented to enable one of ordinary skill in the art tomake and use the invention and is provided in the context of a patentapplication and its requirements. Various modifications to the preferredembodiment and the generic principles and features described herein willbe readily apparent to those skilled in the art.

Although the following describes aspects of digital image data capturethrough a digital camera device, it is meant as an illustrativeembodiment of the features of the present invention. The presentinvention is equally capable of utilization with other devices thatperform digital image data capture and processing, including, but notlimited to, computer systems, including those used to capture digitalimages accessible from Internet sites and image scanner equipment.Further, the data structures and commands discussed with reference to apreferred embodiment are suitably included as part of high level codeused directly by one or more applications that is readily achievedthrough the use of C, C++, or other similar programming language, andstored on a computer readable medium.

A digital camera architecture has been disclosed in co-pending U.S.patent application Ser. No. 08,666,241, entitled "A System And MethodFor Using A Unified Memory Architecture To Implement A Digital CameraDevice.," filed on Jun. 20, 1996, 1996, and assigned to the Assignee ofthe present application. The Applicant hereby incorporates theco-pending application by reference, and reproduces portions of thatapplication herein with reference to FIGS. 1-5 for convenience.

Referring now to FIG. 1, a block diagram of a camera 110 is shownaccording to the present invention. Camera 110 preferably comprises animaging device 114, a system bus 116 and a computer 118. Imaging device114 is optically coupled to an object 112 and electrically coupled viasystem bus 116 to computer 118. Once a photographer has focused imagingdevice 114 on object 112 and, using a capture button or some other means(as described more fully with reference to FIGS. 7 and 8 hereinbelow),instructed camera 110 to capture an image of object 112, computer 118commands imaging device 114 via system bus 116 to capture raw image datarepresenting object 112. The captured raw image data is transferred oversystem bus 116 to computer 118 which performs various image processingfunctions on the image data before storing it in its internal memory.System bus 116 also passes various status and control signals betweenimaging device 114 and computer 118.

Referring now to FIG. 2, a block diagram of the preferred embodiment ofimaging device 114 is shown. Imaging device 114 preferably comprises alens 220 having an iris, a filter 222, an image sensor 224, a timinggenerator 226, an analog signal processor (ASP) 228, ananalog-to-digital (A/D) converter 230, an interface 232, and one or moremotors 234.

U.S. patent application Ser. No. 08/355,031, entitled "A System andMethod For Generating a Contrast Overlay as a Focus Assist for anImaging Device," filed on Dec. 13, 1994, is incorporated herein byreference and provides a detailed discussion of the preferred elementsof imaging device 114. Briefly, imaging device 114 captures an image ofobject 112 via reflected light impacting image sensor 224 along opticalpath 236. Image sensor 224 responsively generates a set of raw imagedata representing the captured image 112. The raw image data is thenrouted through ASP 228, A/D converter 230 and interface 232. Interface232 has outputs for controlling ASP 228, motors 234 and timing generator226. From interface 232, the raw image data passes over system bus 116to computer 118.

Referring now to FIG. 3, a block diagram of the preferred embodiment forcomputer 118 is shown. System bus 116 provides connection paths betweenimaging device 114, power manager 342, central processing unit (CPU)344, dynamic random-access memory (DRAM) 346, input/output interface(I/O) 348, read-only memory (ROM) 350, and buffers/connector 352.Removable memory 354 connects to system bus 116 via buffers/connector352. Alternately, camera 110 may be implemented without removable memory354 or buffers/connector 352.

Power manager 342 communicates via line 366 with power supply 356 andcoordinates power management operations for camera 110. CPU 344typically includes a conventional processor device for controlling theoperation of camera 110. In the preferred embodiment, CPU 344 is capableof concurrently running multiple software routines to control thevarious processes of camera 110 within a multi-threading environment.DRAM 346 is a contiguous block of dynamic memory which may beselectively allocated to various storage functions.

I/O 348 is an interface device allowing communications to and fromcomputer 118. For example, I/O 348 permits an external host computer(not shown) to connect to and communicate with computer 118. I/O 348also permits a camera 110 user to communicate with camera 110 via anexternal user interface and via an external display panel, referred toas a view finder.

ROM 350 typically comprises a conventional nonvolatile read-only memorywhich stores a set of computer-readable program instructions to controlthe operation of camera 110. ROM 350 is further discussed below inconjunction with FIG. 4. Removable memory 354 serves as an additionalimage data storage area and is preferably a non-volatile device, readilyremovable and replaceable by a camera 110 user via buffers/connector352. Thus, a user who possesses several removable memories 354 mayreplace a full removable memory 354 with an empty removable memory 354to effectively expand the picture-taking capacity of camera 110. In thepreferred embodiment of the present invention, removable memory 354 istypically implemented using a flash disk.

Power supply 356 supplies operating power to the various components ofcamera 110. In the preferred embodiment, power supply 356 providesoperating power to a main power bus 362 and also to a secondary powerbus 364. The main power bus 362 provides power to imaging device 114,I/O 348, ROM 350 and removable memory 354. The secondary power bus 364provides power to power manager 342, CPU 344 and DRAM 346.

Power supply 356 is connected to main batteries 358 and also to backupbatteries 360. In the preferred embodiment, a camera 110 user may alsoconnect power supply 356 to an external power source. During normaloperation of power supply 356, the main batteries 358 provide operatingpower to power supply 356 which then provides the operating power tocamera 110 via both main power bus 362 and secondary power bus 364.

During a power failure mode in which the main batteries 358 have failed(when their output voltage has fallen below a minimum operationalvoltage level) the backup batteries 360 provide operating power to powersupply 356 which then provides the operating power only to the secondarypower bus 364 of camera 110. Selected components of camera 110(including DRAM 346) are thus protected against a power failure in mainbatteries 358.

Power supply 356 preferably also includes a flywheel capacitor connectedto the power line coming from the main batteries 358. If the mainbatteries 358 suddenly fail, the flywheel capacitor temporarilymaintains the voltage from the main batteries 358 at a sufficient level,so that computer 118 can protect any image data currently beingprocessed by camera 110 before shutdown occurs.

Referring now to FIG. 4, a memory map showing the preferred embodimentof ROM 350 is shown. In the preferred embodiment, ROM 350 includescontrol application 400, toolbox 402, drivers 404, kernel 406 and systemconfiguration 408. Control application 400 comprises programinstructions for controlling and coordinating the various functions ofcamera 110. Toolbox 402 contains selected function modules includingmemory manager 410, RAM spooler 1 (412), RAM spooler 2 (414), removablememory spooler 1 (416), removable memory spooler 2 (418), imageprocessing and compression 420 and file system 422.

Referring now to FIG. 5, a block diagram showing preferred data pathsfor transmitting image data between selected computer 118 components isshown. In FIG. 5, frame buffer 536 receives and stores raw image datapreviously captured by image device 114. Frame buffer 536 then transferscontrol of the raw image data to RAM spooler 1 (412) via line 610.Alternatively, if RAM disk 532 is full, frame buffer 536 may transfercontrol of the raw image data directly to image processing/compression420 using line 612. If RAM spooler 1 (412) receives control of the rawimage data, it then stores the raw image data into RAM disk 532 usingline 614.

Removable memory spooler 1 (416) may then access the raw image data fromRAM disk 532 via line 616 and store it into removable memory 354 usingline 618. Alternatively, if removable memory 354 is full or is notinserted, RAM disk 532 may provide the raw image data directly to imageprocessing/compression 420 using line 620. If removable memory spooler 1(416) stores the raw image data into removable memory 354, then imageprocessing/compression typically accesses the stored raw image datausing line 622.

Image data is sometimes related among images captured. As mentionedpreviously, time lapse image capture sequences/burst image capturesequence represent a form of `natural` image groups. For purposes ofthis discussion, natural image groups, as their name implies, preferablyrefer to sets of images related naturally by the method of capture.Other capture sequences appropriately considered natural groups includesynchronized images with sound, and video clips with or without sound.Another type of image group is a programmed group. Programmed groupspreferably refer to image groups created by the external host computeror a script within the capture device. Scripts preferably refer tocommand sequences used to access the functions and features of a capturedevice when away from a host computer. Programmed groups includepanorama sequence groups, exposure autobracket groups, and any othertype of user-defined groups. By way of example, user-defined groupsinclude a series of images related by location, such as a real estateagent would produce when taking images of houses and rooms within thehouses.

In a preferred embodiment, a digital camera produces both natural andprogrammed groups. The image groups preferably form a level in ahierarchical system for organizing images in the camera memory, as shownin FIG. 6. Within the camera folder 600 created from the camera serialnumber are natural groups 602 and programmed groups 604, each with theirown associated folder. The still image files and/or movie files areappropriately located within the folders for each of the natural groupsand programmed groups to which they are associated. In addition, in analternate embodiment, programmed groups may also include a naturalgroup, and thus, a natural group folder is suitably provided within theprogram group folder in such situations. Capturing of images for eachgroup type is described in more detail hereinbelow with reference toFIG. 7.

Image Group Formation

An image group is preferably formed as illustrated in the flow chart ofFIG. 7. Initiation of an image group capture session occurs uponissuance of a command sequence for image group capture (step 700), e.g.,via a command such as a StartCapture (CaptureType, CaptureParameters)command. The parameters of the image capture session are also provided(step 702), e.g., via the CaptureType and CaptureParameters specified inthe StartCapture command. The parameters specified suitably provideinformation capable for use as tags for the image files. In an alternateembodiment, a StartCapture command is suitably initiated by the cameracontrol application (400, FIG. 4) upon depressing of the camera'sshutter button. Parameters previously stored for the session are thenappropriately utilized by the camera.

While grouping related images into folders aids in the identification ofrelated images, individual image files within the folders also aresuitably identified by image tags. Image tags preferably provide severalindicators, including what type of group the image files form, whatposition in the sequence of image files each image file represents, andother information to assist in post-processing techniques. For example,post-processing techniques include those used to form a panorama imagefrom a particular image sequence forming a group.

Preferably, the image tags provided include a group type tag. The grouptype tag suitably identifies whether the image file is part of a naturalgroup, programmed group, a single image, etc. The tags further include agroup sequence number tag, where the group sequence number tag containsa number identifying the position of the image file in the sequence ofimage files formed during the image group capture. Other tags includegroup data field tags for storing group-specific information. Groupspecific information for panorama sequences, for example, includes afirst group data tag identifying image overlap data, a second group datatag identifying an angle of view for the lens of the camera, and a thirdgroup data tag identifying a width of the panorama in degrees, which allaid in the processing for the formation of the panorama image.

Thus, for single still image capture, a `0` value suitably is suppliedas the parameter value of the CaptureType, resulting in a tag, such as`sngl`, for the group type tag for the image file. Further, with singleimage captures not requiring specification of any other parameters,suitably, there are no CaptureParameters. For a live image/viewfindercapture, i.e., to a capture a thumbnail image of exactly what the camerais currently seeing for use by the host in presenting a live viewfinderto the user, a CaptureType value of `1` is suitably used. Since captureof exact and current views include out of focus images, suitably, aparameter `preview` allows specification of as a Boolean parameter of`true` or `false` in the CaptureParameters to indicate whether the liveview is to be at a desired setting for a full-size image or is to be atcurrent auto-exposure and auto-focus settings.

For programmed group captures, a CaptureType value of `2` is suitablyused, with tagging of the images by the parameters specified in theCaptureParameters. A group type name is preferably specified in theparameters and is suitably stored as the group type tag. A groupsequence number for the first image in the group, e.g., an unsignedinteger of value `1`, is also specified and stored as the group sequencenumber tag. A parameter for identifying the count sequence as anautocount sequence is preferably also included and set to a true value,e.g., Boolean value `1`, for sequentially tagging each image file in thegroup. A false value suitably sets all file sequence tags for the groupto the same value. Parameters for group specific data are also includedand used as the data for the group data tags. A name for the group isalso capably included in the parameters and stored as the group nametag. The group name appropriately provides the name for the folderholding the image files. When no group name is specified in theparameters, a default name comprising the first two characters of thegroup type name and the image number of the first image captured in thegroup and placed into the folder is suitably used.

By way of example, StartCapture (2, "pano", 1, true, 115, 1850, 180, 0),sets up a programmed group for forming a panorama image. The group typetag is specified by the term "pano". A sequence count initiates from thespecified value of `1` with autocounting, as specified by the `true`parameter. The image files stored suitably also include four data tagsidentifying 115 pixel overlap between images, 18.5° lens angle of view,180° panorama, and a `0` value. With no group name specified in theparameters, suitably a default name is provided, e.g., PAnnnnnn, wherennnnnn is the image number of the first image of the group.

Time-based Image Groups

For natural group captures, the CaptureType is suitably specified as a`3` value. Parameters identified by the CaptureParameters include thegroup type, e.g., burst or time lapse, for the group type tag. A timercount value is also identified, e.g., an unsigned integer value,specifying the number of images to be captured, i.e., the length of theimage capture session. If the count is greater than 1, an initial delayis suitably eliminated, while a count of zero makes the command ano-operation command. A count of `1` results in the group type beingtagged as a single image capture and placed as a still image file withinthe camera folder. Another parameter suitably specified is the timerdelay parameter, which identifies an initial delay if the capture is asingle image capture, or the time between captures for a time lapsesequence. Suitably, values are specified in 0.01 second increments. Acapture size parameter is also preferably identified by an integer valuein a range, e.g., from 1-8, which indicates the size reduction duringcapture. By way of example, legal values of 1, 2, 4, and 8 represent,respectively, reduction sizes of no reduction, 1/4, 1/16, and 1/64.

A time lapse group sequence as an example of a natural group initiateswith a StartCapture (3, "tlap", 10, 6000, 1) command. With theseparameters, the group type tag is "tlap", and the session captures 10images, one every 60 seconds, with no reduction in size during capture.Although not specifically shown in the example, other parameters capablefor inclusion comprise compression level, e.g., a value in a range thatindicates a level of desired compression from minimum to maximum.Additionally, auto-exposure, autofocus, and color or black and whiteindications are also suitably specified, such as with unsigned integerparameter values. The capability to provide such numerous parametersprovides greater flexibility for individualized designation and controlof time lapse capture sessions.

With each subsequent StartCapture command issuance, the CaptureTypevalue suitably indicates whether the image belongs to an initiated imagecapture session, e.g., StartCapture (2) suitably indicates that theimage captured belongs to the programmed group being formed. Each imageis thus suitably captured and tagged (step 704) with each StartCapturecommand issuance. Preferably, the image capture session is thencompleted (step 706) when a completion command occurs, such as when anEndCapture (CaptureType) command is generated from the host, when thecount gets exhausted in a time lapse sequence, or in the alternateembodiment, when the shutter button is no longer being depressed. Whenno CaptureType is identified, e.g., EndCapture (), all capture sessionsare appropriately terminated. When the CaptureType value is `2`, anin-process programmed group capture session is terminated and the groupname is returned. An error is suitably returned when there is noin-process programmed group. When a CaptureType value of `3` isidentified, an in-process natural group sequence is terminated and thegroup name is returned. An error again occurs when no natural groupsequence is in-process. When other values of CaptureType are specified,an error is returned, and the command has no effect. After completion ofan image capture session, other image groups are then suitably formed byrepeating the process.

In terms of controlling captures, FIG. 8 presents a more detailed flowdiagram. Upon receipt of a host or script StartCapture command, adetermination of whether timers are running is made (step 800), i.e.,whether a delay is already in progress for an image capture. If so, anerror is signaled (step 802). If not, the CaptureType specified in theStartCapture command is determined (step 804). When the value is `0`,indicating a still image is to be captured, a `1`, indicating alive/viewfinder image is to be captured, or a `2`, indicating aprogrammed group is to be captured, the process continues with an imagecapture (step 806). Once the capture is completed, the routine is exited(step 808). When there is no memory available, an error is returned(step 802).

When the CaptureType is a `3`, indicating a natural group capture, e.g.,a time lapse sequence, the process continues with the setting of twovariables, e.g., `tldla` to hold a specified TimerDelay value from theCaptureParameters of the StartCapture command (step 810), and `tlcnt` tohold a specified TimerCount value from the CaptureParameters (step 812).A determination of the tlcnt value is made (step 814), and when equal tozero, the process is completed (step 816). When the tlcnt value is equalto 1, the delay as specified in the tldla value is waited (step 818) andthe tlcnt is reduced by one (step 820) before an image is captured (step822). When the tlcnt is greater than 1, the tlcnt value is reduced by 1(step 820), and an image is captured (step 822). If no memory isavailable, the process is exited (step 816). Alternatively, when thecapture is done, the value of tlcnt is again determined (step 824). Whenthe tlcnt count value has been exhausted, the process is exited (step816). When the tlcnt count value has not been exhausted, the delay timeis again waited (step 818), and the process proceeds as described untilan exiting situation occurs. Included in the exiting situations is anabort or EndCapture occurrence. An EndCapture command results from ahost, as described previously, while an abort command may occur whenpower fails, or when another StartCapture command with a differentCaptureType occurs to prematurely end an image capture session.

Of course, for a situation in which a natural group is being capturedwithin a programmed group, the issuance of a StartCapture command with adifferent CaptureType suitably does not end the programmed groupcapture. Rather, with the preferred EndCapture command definition inwhich a programmed group is ended by specification of the group type,e.g., EndCapture (2), a natural group is suitably included by issuing aStartCapture (3)/EndCapture (3) sequence within the programmed groupsession.

Coherent Memory Management of Image Groups

The image group captured during an image capture session preferablyforms a level of the hierarchy within the camera memory, as discussedpreviously. Management of the image grouping for such a hierarchy iscomplicated by the presence of multiple memory components, including RAMdisk 532 (FIG. 5) and removable memory 354 (FIG. 3). Suitably, with theassumption that the RAM disk 532 is too small to accommodate a compleximage grouping system, image files are appropriately stored as a flathierarchy. An image queue within the DRAM 346 (FIG. 3) capably containsthe folder information for the image files, so that image file groupingby tag occurs with folder creation only when the files are moved orspooled from the RAM disk 532 to a removable memory 354. The inclusionof the group name, i.e., the folder name, in the image tags in thefiles, and in the image queue, ensures that proper creation of thehierarchy readily occurs once a removable memory 354 is inserted.

With a hierarchy on the removable memory 354 and none on the RAM disk532, proper maintenance of image files in the hierarchy is needed forthose situations in which all of the images in a group do not fit on theremovable memory 354, and one or more files of the group must then bestored on the RAM disk 532. In a preferred embodiment, an alias file isused within the removable memory 354 hierarchy for each of the imagefiles missing from the removable memory 354. The alias file ispreferably zero sectors in size, and has the same name as the missingfile, but with a SUB (for substitute) extension. When the images aresubsequently transferred to a host system, the correct image filesuitably replaces the substitute file via the user or host software.

Although the present invention has been described in accordance with theembodiments shown, one of ordinary skill in the art will recognize thatthere could be variations to the embodiment and those variations wouldbe within the spirit and scope of the present invention. For example,the values and value types described for the parameters and commandnames are illustrative of a preferred approach, and they may be alteredto suit particular needs. Accordingly, many modifications may be made byone of ordinary skill without departing from the spirit and scope of thepresent invention, the scope of which is defined by the followingclaims.

What is claimed is:
 1. A method for maintaining coherent imagerelationships within identified image groups in a memory system of adigital image capture device, the method comprising:storing a pluralityof groups of related images on a removable storage device in ahierarchical manner; and providing an alias identifier for an image filewhen the removable storage device has reached its storage capacity,wherein the alias identifier identifies the image file stored in astorage device of the digital image capture device, wherein the imagefile is provided with a same file name and a substitute extensiondesignation to correlate the image file on the storage device with anempty file of the same name on the removable storage device.
 2. Themethod of claim 1 wherein the removable storage device further comprisesa flash disk storage device.
 3. The method of claim 1 wherein thestorage device of the digital image capture device further comprises aRAM disk storage device.
 4. The method of claim 3 further comprisingincluding at least one parameter associated with the image file toensure that the image file is associated with an appropriate imagegroup.
 5. The method of claim 4 wherein the at least one parameterfurther comprises a group name.
 6. A system for maintaining coherentimage relationships within identified image groups, the systemcomprising:a digital image capture device, the digital image capturedevice comprising removable and system storage devices, and further, thedigital image capture device capable of processing digital image datainto image files for storage in image groups on the removable storagedevice in a hierarchical manner, wherein the hierarchy comprises a flathierarchy encompassing image files grouped by tags and within each groupthe files are related to each other; and a central processing unitwithin the digital image capture device and capable of coordinatingprovision of an alias identifier for an image file when the removablestorage device has reached its storage capacity, wherein the aliasidentifier identifies the image file stored in the system storage deviceof the digital image capture device, wherein the alias identifierfurther comprises a same file name and a substitute extensiondesignation to correlate the image file on the system storage devicewith an empty file of the same name on the removable storage device. 7.The system of claim 6 wherein the removable storage device furthercomprises a flash disk.
 8. The system of claim 6 wherein the systemstorage device further comprises a RAM disk.
 9. The system of claim 8wherein the image file further includes at least one parameter to ensurethat the image file is associated with an appropriate image group. 10.The system of claim 9 wherein the at least one parameter furthercomprises a group name.
 11. A computer readable medium containingprogram instructions for maintaining coherent image relationships withinidentified image groups in a memory system of a digital image capturedevice comprising:storing a plurality of groups of related images on aremovable storage device in a hierarchical manner, wherein the hierarchycomprises a flat hierarchy encompassing image files grouped by tags andwithin each group the files are related to each other; and providing analias identifier for an image file when the removable storage device hasreached its storage capacity, wherein the alias identifier identifiesthe image file stored in a storage device of the digital image capturedevice, wherein the image file is provided with a same file name and asubstitute extension designation to correlate the image file on thestorage device with an empty file of the same name on the removablestorage device.